Limiting mobile device functionality in a vehicle

ABSTRACT

A method, device and system for limiting mobile device functionality in a vehicle. When a vehicle is in motion, a motion detector initiates a signal generator, which transmits a disabling signal that is received and processed by software residing on a mobile device. Upon receipt and validation of the disabling signal, the software will alter the mobile device&#39;s system configuration to, for example, remove the ability of the mobile device to respond to typing and other touch screen functions and to send and/or receive text and/or e-mail messages for as long as the disabling signal is transmitted. Once the motion detector detects that the vehicle is no longer in motion, the signal generator ceases transmission of the disabling signal. After a predetermined time of not receiving a disabling signal, the software restores the mobile device&#39;s system configuration to its original configuration.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation-in-part application of U.S. patentapplication Ser. No. 14/212,740, filed Mar. 14, 2014, entitled “LimitingMobile Device Functionality in a Vehicle”, which claims priority to U.S.Provisional Patent Application No. 61/801,025, filed Mar. 15, 2013,entitled “Method and System for Limiting Mobile Device Functionality ina Vehicle”, both of which are hereby incorporated by reference herein intheir entireties.

FIELD OF INVENTION

The present disclosure generally relates to mobile devices and vehicles;more specifically, to detecting the motion status of a vehicle andaltering the operating state of the mobile device based on the motionstatus.

BACKGROUND

The personal, societal, and economic impacts of texting while drivingare well chronicled. Studies show that texting while driving increasesthe risk of an accident by 2300%. Texting while driving resulted in16,141 deaths in the U.S. between 2001 and 2007, and in 2009, 5,474people were killed in the U.S. because of accidents that involveddistracted driving. Another 448,000 were injured.

Younger generations have grown up using texting and email from a veryyoung age. Most teenagers send hundreds, if not thousands, of texts eachweek, making it their primary form of communication. It is an engrainedhabit. Stepping away from it voluntarily, even when presented with thedangers to themselves and others they may impact, is very difficult. Theincreasing amount of accidents, cost, injuries, and deaths is alarming.

Current systems have attempted to address this issue but have majordrawbacks. Such drawbacks include reliance on multiple voluntary actionsby the driver and/or reliance on the motion of the vehicle (i.e. acertain minimum speed). There are many documented crashes involving adriver texting while driving at a slow speed, such as rolling slowlythrough a stop or red light into an intersection. Some systems rely onwireless transmissions, such as conventional Bluetooth®, that requiresynchronization with each vehicle. Some systems also gather driverperformance data, such as speed or number of hard stops. Such systemsmay be considered intrusive on the driver's privacy. Many systems can bereadily defeated by a driver determined to do so. In addition, somesystems' components can be disabled without accountability to amonitoring entity.

As such, there is a need in the art for a system that can automaticallylimit mobile device functionality, including the ability to text, when avehicle is in operation.

SUMMARY

In accordance with the teachings disclosed herein, embodiments relatedto a method, device, and system for limiting mobile device functionalityin a vehicle are disclosed. The vehicle has a disabling deviceassociated therewith and the disabling device comprises a motiondetector.

In an embodiment, the system comprises a disabling device and a mobiledevice. The disabling device has a motion detector, a microcontroller,and a signal generator. The microcontroller, which is in communicationwith the motion detector, receives a motion status of the vehicle fromthe motion detector. The signal generator, which is in communicationwith the microcontroller, transmits a disabling signal when it receivesthe motion status of the vehicle indicating that the vehicle is inmotion. The mobile device, which has a software application residingthereon, receives the disabling signal. The software application altersthe mobile device's system configuration responsive to the receiveddisabling signal.

In an additional embodiment, the disabling device comprises a motiondetector, microcontroller and a signal generator. The microcontroller,which is in communication with the motion detector, receives a motionstatus of the vehicle from the motion detector. The signal generator,which is in communication with the microcontroller, transmits adisabling signal when it receives the motion status of the vehicleindicating that the vehicle is in motion.

In another embodiment, a method comprises detecting, at the motiondetector, a motion status of the vehicle. A disabling signal istransmitted to a mobile device in communication with the disablingdevice. The disabling signal is transmitted as long as the motion statusof the vehicle indicates the vehicle is in motion. The determination ofthe motion status may repeat continuously or periodically. The disablingsignal triggers a software application on the mobile device to limit thefunctionality of the mobile device.

In further embodiment, a method comprises polling, at a mobile device,for a disabling signal. The disabling signal originates at a disablingdevice. Once a disabling signal is received by the mobile device and itis determined that the disabling signal is valid, the mobile device'ssystem configuration is altered by a software application on the mobiledevice. The mobile device continues polling for the disabling signal.The mobile device's system configuration is restored when the disablingsignal is not received for a pre-determined amount of time.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system for limiting mobile devicefunctionality in a vehicle according to an embodiment of the presentinvention.

FIG. 2 is a flowchart of a method of limiting mobile devicefunctionality in a vehicle from the perspective of the disabling deviceaccording to an embodiment of the present invention.

FIG. 3 is a flowchart of a method of limiting mobile devicefunctionality in a vehicle from the perspective of the disabling deviceaccording to another embodiment of the present invention.

FIG. 4 is a flowchart of a method of issuing monitoring alerts from theperspective of the disabling device according to an embodiment of thepresent invention.

FIG. 5 is a flowchart of method of monitoring three exemplary eventsfrom the perspective of the disabling device according to an embodimentof the present invention.

FIG. 6 is a block diagram illustrating an exemplary mobile device onwhich at least a portion of the method of limiting mobile devicefunctionality in an operating vehicle may occur according to anembodiment of the present invention.

FIG. 7 is a flowchart of a method of limiting device functionality in anoperating vehicle from the perspective of the mobile device according toan embodiment of the present invention.

FIG. 8 is a flowchart of a method of limiting mobile devicefunctionality in a vehicle from the perspective of the mobile deviceaccording to an embodiment of the present invention.

FIGS. 9A through 9C are flowcharts of methods of issuing monitoringalerts from the perspective of the mobile device according to anotherembodiment of the present invention.

DETAIL DESCRIPTION OF THE EMBODIMENTS

A detailed description of the embodiments for a system, device, andmethod for limiting mobile device functionality in an operating vehiclewill now be presented with reference to FIGS. 1 through 9. One of skillin the art will recognize that these embodiments are not intended to belimitations on the scope, and that modifications are possible withoutdeparting from the spirit thereof. In certain instances, well-knownmethods, procedures, components, and circuits have not been described indetail.

In an embodiment, as shown in FIG. 1, system 100 comprises disablingdevice 101 and mobile device 102. Disabling device 101 can be mounted,installed or otherwise positioned in a vehicle, such as for examplecars, trucks, buses, motorcycles, trains and other motor vehicles.Disabling device 101 may be encased in a compact enclosure, such as apolycase. Disabling device 101 may be compact for discrete mounting on avehicle windshield. Disabling device may be positioned on the interiorof the vehicle at or near the corner of the windshield, on thewindshield near the rearview mirror or at another location within thevehicle. Disabling device 101 comprises motion detector 103, processoror microcontroller unit (MCU) 104 in communication with motion detector103, cellular radio 105 in communication with MCU 104, signal generator106 in communication with MCU 104, power source 108 in communicationwith motion detector 103, MCU 104, cellular radio 105, and signalgenerator 106. Disabling device 101 may optionally comprise backup powersource 112 in communication with MCU 104. Backup power source 112 mayalso be in communication with one or more of motion detector 103,cellular radio 105, and signal generator 106. Disabling device mayoptionally comprise solar cell 109 in communication with power source108. Solar cell 109 may also be in communication with backup powersource 112. Mobile device 102, further shown and described below and inFIG. 6, has a software application, or app, (e.g. Device OwnerApplication (DOA), mobile device management system or other applicablesoftware) residing thereon that is capable of receiving a disablingsignal from disabling device 101.

Motion detector 103 determines the motion status of a vehicle. Motiondetector 103 may be, for example, an accelerometer, a gyroscope or bothan accelerometer and a gyroscope. Motion detector 103 may detect, forexample, acceleration, direction (up/down/forward/backward), speed or acombination thereof. Motion detector 103 transmits a signal comprisingthe motion status to MCU 104. Upon arrival at MCU 104, the signal isconverted into a signal readable by MCU 104. This can be accomplished,for example, through the use of peripheral interface technology such asUART/SPI (universal asynchronous receiver/transmitter/serial peripheralinterface) or 12C (Inter-Integrated Circuit).

MCU 104 uses the motion status within the signal received from motiondetector 103 to ascertain the motion status of the vehicle. If themotion status indicates that the vehicle is in motion, MCU 104 instructssignal generator 106 to broadcast a disabling signal. MCU 104 interfaceswith signal generator 106, which may be, for example, a 802.11 radio, aBluetooth® beacon, a Bluetooth® low energy beacon or any device that cantransmit a similar electronic signal or trigger (which may optionallycomprise an identifier), via any known mechanism, for example, UART orSPI. Motion detector 103 may detect movement of the vehicle causing itto produce a motion status indicating that the vehicle is in motion.Alternatively, motion detector 103 may only produce a motion statusindicating that the vehicle is in motion once the motion has surpassed acertain threshold, such as, for example a pre-determined speed, apredetermined acceleration or a combination thereof. If the vehicle isnot moving or alternatively, has not exceeded a movement threshold,motion detector 103 may produce a motion status indicating that thevehicle is not in motion. Alternatively, motion detector may not producea signal, which may be interpreted by MCU 104 to mean that the vehiclewas not in motion and that the motion status should so indicate. MCU 104may continuously or periodically monitor motion detector 103 for vehiclemovement.

If a disabling signal has been broadcast and mobile device 102 is inrange of the broadcasting signal, the software residing on mobile device102 will alter the system configuration of mobile device 102 to restrictthe user's ability to perform certain tasks including, for example,using the keyboard, using the touch screen or sending and/or receivingtext messages, email messages, and/or phone calls. Use of some features,such as maps, dialing 911 and voice-activated calling can still bepermitted. Broadcast of the disabling signal will continue or beperformed at regular intervals (e.g. every 20 seconds) until the motionstatus indicates that that the vehicle is not in motion. The disablingsignal can be, for example, a Bluetooth® low energy beacon signal (ortransmission). The broadcasting range of the disabling signal can belimited to only encompass the driver area or vehicle (e.g. 3-10 feet).The broadcast of the disabling signal may continue after the motionstatus of the vehicle becomes non-moving for a predetermined amount oftime (e.g. one to two minutes).

MCU 104 ensures disabling device 101's operation by checking forconnectivity to other disabling device components and for installationin and/or removal from a vehicle. This can be accomplished with internalprogramming and/or a physical or software switch. As an example ofmonitoring for installation and/or removal, if disabling device isattached to the vehicle (for example, on the windshield) using suctioncups or adhesive or another similar mounting mechanism, a pressureswitch can be used to detect installation and/or removal of thedisabling device. In addition, MCU 104 monitors power source 108 for thestatus of the power supply.

System 100 can further include monitoring party's device 111. Cellularradio 105 communicates wirelessly with monitoring party's device 111.Monitoring party's device 111 may monitor the status of disabling device101 and the app running on mobile device 102. Cellular radio 105 may useGSM cellular modules (global system for mobile communications) or anyother known transmission service. Cellular radio 105 may include asubscriber identity module (SIM) card and may be equipped with SMS textcapabilities. Cellular radio 105, at the direction of MCU 104, can sendmessages/alerts, such as, for example a short message service (SMS) pushnotification comprising an identifier of the disabling device tomonitoring party's device 111, when certain events occur. For example, amessage may be sent when disabling device 101 is activated, whendisabling device 101 is removed from the vehicle, when the availablepower in power source 108 or back-up power source 112 is low or whencellular radio 105 has low cellular service as well as periodic alertsshowing the device is working properly. The app running on mobile device102 can also send notifications, such as ‘app installed’, ‘appdisabled’, or ‘app functioning normally’, to monitoring party's device111. The notifications from the app may include mobile device 102'sphone number. A monitoring party may be an insurance company or aconcerned parent. Monitoring party's device 111 enables the monitoringparty to receive information verifying that disabling device 101 and theapp running on mobile device 102 are operational.

Power source 108 may be, for example, a battery or a long life battery.Power source 108 may provide power to MCU 104, motion detector 103,cellular radio 105, and/or signal generator 106 if the element itself isnot self-powered or it may serve as a secondary power source for anyself-powered element. Disabling system may be hard-wired to the vehicleit is installed in. In this case, MCU 104, motion detector 103, cellularradio 105, and/or signal generator 106 may draw power from the vehicle'spower source. Power source 108 may then be used in the event disablingdevice 101 is removed from the vehicle or the hard-wired connection issevered.

Backup power source, which may be for example a backup battery, mayprovide power to MCU 104 and cellular radio 105 to allow cellular radio105 to send an alert to monitoring party 111 when MCU 104 detects thatthe power available in power source 108 is low. Backup power source 112may also provide power to signal generator 106 and motion detector 103when the power available from power source 108 is low to allow disablingdevice 101 to operate continuously.

MCU 104 may also store information related to the driver/user or to thevehicle disabling device 101 is attached to. Such information mayinclude the account number and name of the user and the make, year,and/or model of the vehicle. Such information can also be transmitted,as needed, via cellular radio 103 to, for example, monitoring party'sdevice 111, or via signal generator 106 to, for example, mobile device102.

Solar cell 109 may be used to recharge power source 108 and/or backuppower source 112.

System 100 may further include remote server 113 having a database(whitelist) containing a list of media access control (MAC) addresses orother unique identifier assigned to the signal generator of eachdisabling device in operation. Remote server 113 may be inbi-directional, wireless communication with mobile device 102. Thislist, or whitelist, can be queried by the software running on a mobiledevice to determine if a received disabling signal is coming from avalid source. This may prevent a bad actor from attempting to disable aphone by sending a disabling signal from an unauthorized device.

An embodiment of a method of the present invention from the perspectiveof disabling device 101 (method 300) is illustrated in the flowchart inFIG. 2 with reference to disabling device 101 of FIG. 1. As shown inoperation 305, disabling device 101 receives the motion status of thevehicle from motion detector 103. If, in operation 315, the motionstatus indicates that the vehicle is not in motion, disabling device 101continues receiving the motion status from motion detector 103.Otherwise, disabling device 101, in operation 320, transmits a disablingsignal using signal generator 106. Disabling device 101 then repeats theprocess. Optionally, disabling device 101 can, in operation 325, wait apredetermined amount of time before repeating this process.

Another embodiment of a method of the present invention from theperspective of disabling device 101 (method 400) is illustrated in theflowchart of FIG. 3 with reference to disabling device 101 of FIG. 1. Asshown, method 400 begins initially with the disabling signal turned off.In operation 405, disabling device 101 receives the motion status of thevehicle from motion detector 103. If, in operation 415, the motionstatus indicates that the vehicle is in motion, disabling device 101, inoperation 420, transmits a disabling signal using wireless signalgenerator 106. Broadcast of the disabling signal continues while thevehicle is in motion. Disabling device 101 then repeats the process.Optionally, disabling device 101 can, in operation 425, wait apredetermined amount of time before repeating this process. If, inoperation 415, the motion status indicates that the vehicle is not inmotion, then disabling device 101, in operation 430, determines if thedisabling signal is turned on. If the disabling signal is off, then theprocess repeats. If the disabling signal is on, then it is turned off inoperation 440 and the process repeats. Optionally, disabling device 101can, in operation 440, wait a predetermined amount of time beforeturning off disabling signal and repeating the process. Waiting apredetermined amount of time (e.g. one to two minutes) before repeatingthe process, allows for the host vehicle to come to a temporary stop(e.g. at a stop light or stop sign) without allowing the mobile deviceto return to normal operations.

Optionally, MCU 104 can monitor signal generator 106 for endpointconnectivity (e.g. a connection to mobile device 102) if suchconnectivity is possible with the technology used for the signalgenerator. Once a connection is established, disabling device 101 cansend a wireless signal or notification to mobile device 102.

As discussed previously, cellular radio 105, at the direction of MCU104, can send alerts, such as, for example a short message service (SMS)push notification, to monitoring party's device 111, when certain eventsoccur. An embodiment of a portion of the method of the present inventionthat issues these alerts is shown in FIG. 4. In operation 505 of method500, disabling device 101 determines whether a monitoring event hasoccurred. If, in operation 510, a monitoring event has occurred, analert will be transmitted to monitoring party's device 111 in operation515. If, in operation 510, no monitoring event has occurred, thendisabling device 101 continues checking for a monitoring event.

Monitoring events may include disabling device 101 being removed from ahost vehicle, disabling device 101 being secured in a host vehicle, ordisabling device 101 losing power for a predetermined amount of time. Amethod of monitoring these three exemplary events (method 600) isillustrated in FIG. 5 with reference to disabling device 101 of FIG. 1.In operation 605, disabling device 101 determines if it has been newlyinstalled in a host vehicle. If disabling device has been newlyinstalled, then, in operation 610, cellular radio 105 sends an alert tomonitoring party's device 111 indicating that the initial installationof disabling device 101 is complete. If the disabling device has notbeen newly installed, then, in operation 615, disabling device 101determines if it has been removed from the vehicle. If disabling device101 has been removed from the vehicle, then, in operation 620, cellularradio 105 sends an alert to monitoring party's device 111 indicatingthat disabling device 101 has been removed. If disabling device 101 isstill installed, disabling device 101 determines if it has lost powerfrom power source 108 for a predetermined amount of time (e.g. twominutes). This can be determined by monitoring MCU 104's interface withpower source 108. If disabling device 101 has lost power from powersource 108 for a predetermined amount of time, cellular radio 105, whichmay be powered by backup power source 112 or its own power source, sendsan alert to monitoring party's device 111 indicating that disablingdevice 101 has lost power from power source 108. If disabling device 101has not lost power from power source 108, then the process continuesmonitoring for disabling device 101's removal from the vehicle(operation 615) and disabling device 101 losing power from power source108 (operation 625).

Disabling device 101 can also perform a self-test to ensure that itsdisabling signal is transmitting and power source 108 is operational. Amonitoring alert can then be sent at pre-determined intervals (e.g.every 30 days) to monitoring party's device 111 indicating thatdisabling device 101 is functioning properly.

FIG. 6 is a block diagram showing a mobile device according to anexemplary embodiment, which may be, for example mobile device 102 asdescribed above and shown in FIG. 1. The exemplary mobile deviceincludes memory 701, processor 702 and user interface module 703, whichincludes touch-screen display module 704 and tactile feedback module705, all of which is described in further detail below. It should beunderstood, that a mobile device as illustrated and hereinafterdescribed is merely illustrative of a mobile device that could benefitfrom embodiments of the invention and, therefore, should not be taken tolimit the scope of the invention. While one embodiment of the mobiledevice is illustrated for purposes of example, other types of mobileelectronic devices, such as, but not limited to, mobile phones, smartphones, portable digital assistants (PDAs), tablets, mobile computingdevices, gaming devices, laptop computers, media players, and othertypes of mobile electronic systems, may readily employ embodiments ofthe invention.

An embodiment of the method of the present invention from theperspective of mobile device 102 (method 800) is illustrated in theflowchart of FIG. 7. As shown in operation 805, software running onmobile device 102 polls for a disabling signal. Once a disabling signalis received (in operation 810), the software determines if it is validin operation 815. If the disabling signal is not valid, the softwarecontinues polling for a disabling signal in operation 805. If thedisabling signal is valid, then the software alters the systemconfiguration of mobile device 102 in operation 820 to restrict theuser's ability to perform certain tasks. These tasks may include, forexample, using the keyboard, or sending and/or receiving text messagesand/or email messages, placing and/or receiving phone calls, or placingand/or receiving phone calls when not in hands-free mode. In operation825, the software continues to poll for a disabling signal. In operation830, the software determines if the same disabling signal has beenreceived within a predetermined period of time. If it has, then thesoftware continues to poll for a disabling signal (operation 825). Ifthe same disabling signal has not been received within a predeterminedperiod of time, the software restores the system configuration of mobiledevice 102 in operation 835.

Another embodiment of the method of the present invention from theperspective of mobile device 102 (method 900) is illustrated in theflowchart of FIG. 8. As shown in operation 905, software running onmobile device 102 polls for a disabling signal. The disabling signal,which may be, for example a Bluetooth® beacon signal (or transmission),includes identifiers, such as, for example, a universally uniqueidentifiers (UUID) or a MAC address. Once a disabling signal is received(in operation 910), the software queries, in operation 920, a locallylocated list of known identifiers to determine, in operation 940, if theidentifier received in the disabling signal is contained in the locallist. If the identifier is not in the local list, then, in operation945, a remotely located list of known identifiers is queried todetermine, in operation 950, if the identifier is contained in theremote list. If the identifier is not contained in the remote list, theidentifier is not recognized and the software continues polling for adisabling signal in operation 905. If the MAC address is contained inthe remote list, the MAC address is added to the local list in operation955. Once a valid MAC address has been confirmed, the software altersthe system configuration of mobile device 102 in operation 920 torestrict the user's ability to perform certain tasks including, forexample, using the keyboard, or sending and/or receiving text messages,email messages, and/or phone calls. In operation 925, the softwarecontinues to poll for a disabling signal. In operation 930, the softwaredetermines if the same network identifier has been received within apredetermined period of time. If it has, then the software continues topoll for a disabling signal (operation 925). If the same disablingsignal has not been received within a predetermined period of time, thesoftware restores the system configuration of mobile device 102 inoperation 935.

Like disabling device 101, the software running on mobile device 102 canprotect itself from tampering and verify its own operable status bytransmitting alerts, such as, for example, a SMS push notificationcontaining, for example, mobile device 102's phone number, to monitoringparty's device 111. Monitoring events can include the software beinginstalled on mobile device 102 or the software being disabled. Thesoftware running on mobile device 102 may comprise two separate apps—aprimary system app and a secondary app. The primary app may be monitoredby the secondary app. The purpose of the secondary app is to send analert to monitoring party device 111 in the event of removal of theprimary app. The primary app also monitors the secondary app and sendsan alert to monitoring party device 111 in the event of removal of thesecondary app. In this respect the primary and secondary appindependently monitor each other for removal, making the app portion ofthe system self-protecting. Methods (methods 1000, 1015, and 1030) thatissue exemplary alerts originating from mobile device 102 are shown inFIGS. 9A through 9C.

As shown in FIG. 9A, method 1000 determines, in operation 1005, if theprimary app and the secondary app have been newly installed on mobiledevice 102. If the software has been newly installed, then, in operation1010, mobile device 102 sends an alert to monitoring party's device 111indicating that the software installation has been completed.

As shown in FIG. 9B, method 1015 determines, in operation 1020, if theprimary app or the secondary app has been removed. If either app hasbeen removed, then, in operation 1025, an alert is sent to monitoringparty's device 111 indicating that the primary app or secondary app (asapplicable) has been removed.

As shown in FIG. 9C, method 1030 determines, in operation 1035, ifmobile device 102 has received a disabling signal. If no disablingsignal has been received, then the software continues to wait for thedisabling signal to arrive. If a disabling signal has been received,then, in operation 1040, the software determines if it is the first timemobile device 102 is receiving the disabling signal. If this is not thefirst time mobile device 102 has received a disabling signal, then thesystem configuration of mobile device 102 is altered in operation 1050.If this is the first time mobile device 102 has received a disablingsignal, then, in operation 1045, an alert is sent to monitoring party'sdevice 111 indicating that the software installation and communicationwith disabling device 102 has completed. The system configuration ofmobile device 102 is then altered in operation 1050. After mobile device102's system configuration has been altered, the software, in operation1055, determines if a predetermined amount of time (e.g. two minutes)has lapsed since mobile device 102 received a disabling signal. If not,then the software continues polling for a disabling signal in operation1035. If the predetermined amount of time has lapsed then the softwarerestores the system configuration of mobile device 102 in operation1060.

The software running on mobile device 102 can also perform a self-testto ensure that it is receiving disabling signals at expected intervals(e.g. every 15 seconds or twice within any 30 second window) and it isaltering mobile device 102's system configuration upon receipt of avalid disabling signal. A monitoring alert can then be sent atpre-determined intervals (e.g. every 30 days) to monitoring party'sdevice 111 indicating that the software running on mobile device 102 isfunctioning properly.

The following are exemplary scenarios demonstrating pre-operationalfunctionality of embodiments of the present invention.

Disabling device set-up—the disabling device is intact but not in thevehicle:

-   -   Motion detector: Inactive    -   Power source (battery): Inactive (charged)    -   MCU: Inactive    -   Signal generator: Inactive    -   Cellular Radio: Inactive

Disabling device installed—the vehicle is not moving:

-   -   Motion detector: Power available from disabling device's battery    -   Power source (battery): Inactive (charging)    -   MCU: Recognizes connectivity to the motion detector via internal        programming, physical switch or software switch and initiates a        monitoring alert (e.g. push notification); analyzes the signal        from the motion detector for the motion status of the vehicle    -   Signal generator: Inactive    -   Cellular Radio: Transmits ‘Disabling device installed’ alert to        the monitoring party's device

Vehicle not moving; disabling device installed:

-   -   Motion detector: Active    -   Power source (battery): Active    -   MCU: Active; monitoring the motion detector    -   Signal generator: Inactive    -   Cellular Radio: Inactive

Disabling device is removed:

-   -   Motion detector: Inactive    -   Power source (battery): Active (discharging); Powers the MCU and        the cellular radio    -   MCU: Recognizes the lack of connectivity of the disabling device        to the vehicle via internal programming, physical switch or        software switch; engages the battery and initiates a monitoring        alert indicating that the disabling device has been disconnected    -   Signal generator: Inactive    -   Cellular Radio: Transmits monitoring alert (e.g. push        notification) indicating that the disabling device has been        disconnected to the monitoring party's device

The following are exemplary scenarios demonstrating operationalfunctionality of embodiments of the present invention.

Vehicle not moving; disabling device installed:

-   -   Motion detector: Power available from disabling device battery    -   Power source (battery): Active (charging)    -   MCU: Recognizes connectivity to the motion detector via internal        programming, physical switch or software switch; analyzes the        signal from the motion detector for the motion status of the        vehicle    -   Signal generator: Inactive    -   Cellular Radio: Inactive

Vehicle moving; disabling device installed

-   -   Interface: Power available from the disabling device is battery    -   Power source (battery): Active    -   MCU: Recognizes connectivity to the motion detector via internal        programming, physical switch, or software switch; analyzes the        signal from the motion detector for the motion status of the        vehicle    -   Signal generator: Sends the disabling signal nominally every        twenty (20) seconds    -   Cellular Radio: Inactive

Vehicle in motion or not in motion; disabling device Installed; powerfrom (primary) battery is unavailable for a predetermined period of time(e.g. two minutes)

-   -   Motion detector: Inactive    -   Power source (Primary battery): Inactive; not charging    -   Backup Power Source (Back-up battery): Active; Powers the MCU        and the cellular radio    -   MCU: Recognizes connectivity to the motion detector via internal        programming, physical switch or software switch; analyzes the        signal from the motion detector for the motion status of the        vehicle; recognizes (primary) battery power is unavailable for        predetermined period of time (e.g. two minutes); initiates        monitoring alert (e.g. push notification) indicating no        (primary) battery power to the disabling device for a defined        time period    -   Signal generator: Inactive    -   Cellular Radio: Transmits a monitoring alert to the monitoring        party's device that the (primary) battery is not operational

Exemplary Electronic Devices—Mobile Device and Disabling Device

FIGS. 1 and 6 are block diagrams illustrating exemplary embodiments ofdisabling device 101 and mobile device 102, respectively. It should beunderstood these exemplary embodiments are merely illustrative ofdisabling device and a mobile device that could benefit from embodimentsof the invention and, therefore, should not be taken to limit the scopeof the invention. Moreover, the apparatus of an example embodiment neednot be the entire device, but may be a component or group of componentsof the device in other example embodiments.

Regarding mobile devices, devices may readily employ embodiments of theinvention regardless of their intent to provide mobility. In thisregard, even though embodiments of the invention are described inconjunction with a mobile device, it should be understood thatembodiments of the invention may be utilized in conjunction with avariety of other electronic devices.

The devices may each comprise a processor or other processing circuitry.As used in this application, the term ‘circuitry’ refers to at least allof the following: hardware-only implementations (such as implementationsin only analog and/or digital circuitry) and to combinations of circuitsand software and/or firmware such as to a combination of processors orportions of processors/software including digital signal processor(s),software, and memory(ies) that work together to cause an apparatus, suchas a mobile phone or tablet, to perform various functions and tocircuits, such as a microprocessor(s) or portion of a microprocessor(s),that require software or firmware for operation, even if the software orfirmware is not physically present. This definition of ‘circuitry’applies to all uses of this term in this application, including in anyclaims.

As a further example, as used in this application, the term “circuitry”would also cover an implementation of merely a processor, multipleprocessors, or portion of a processor and its (or their) accompanyingsoftware and/or firmware.

Further, the processor(s) may comprise functionality to operate one ormore software programs, which may be stored in memory and which may,among other things, cause the processor to implement at least oneembodiment including, for example, one or more of the functionsdescribed above. The mobile device may comprise a user interface forproviding output and/or receiving input. The mobile device may comprisean output device such as a ringer, a conventional earphone and/orspeaker, a microphone, a display, and/or a user input interface, whichare coupled to the processor. The user input interface, which allows theelectronic device to receive data, may comprise means, such as one ormore devices that may allow the electronic device to receive data, suchas a keypad, a touch display, for example if the display comprises touchcapability, and/or the like.

The devices may comprise a memory device including, in one embodiment,volatile memory, such as volatile Random Access Memory (RAM) including acache area for the temporary storage of data. The devices may alsocomprise other memory, for example, non-volatile memory, which may beembedded and/or may be removable. The non-volatile memory may comprisean EEPROM, flash memory or the like. The memories may store any of anumber of pieces of information, and data. The information and data maybe used by the devices to implement one or more functions of thedevices.

Although FIGS. 1 and 6 illustrate an example of a disabling device andmobile device, respectively, that may utilize embodiments of theinvention including those described and depicted, for example, in FIGS.2 through 5 for the disabling device and in FIGS. 7 through 9 for themobile device, the disabling device of FIG. 1 and the mobile device ofFIG. 6 are each merely an example of devices that may utilizeembodiments of the invention.

Embodiments of the invention may be implemented in software, hardware,application logic or a combination of software, hardware, andapplication logic. The software application logic and/or hardware mayreside on the apparatus, a separate device, or a plurality of separatedevices. If desired, part of the software application logic and/orhardware may reside on the apparatus, part of the software, applicationlogic and/or hardware may reside on a separate device, and part of thesoftware, application logic and/or hardware may reside on a plurality ofseparate devices. In an example embodiment, the application logic,software or an instruction set is maintained on any one of variousconventional computer-readable media. In the context of this document, a“computer-readable medium” may be any tangible media or means that cancontain, or store the instructions for use by or in connection with aninstruction execution system, apparatus, or device, such as a computer,with two examples of a computer described and depicted in FIGS. 1 and 6.A computer readable medium may comprise a computer-readable storagemedium that may be any tangible media or means that can contain or storethe instructions for use by or in connection with an instructionexecution system, apparatus, or device, such as a computer.

Alternative embodiments of the present invention include use of the appfor altering the system configuration of mobile device that enter acertain area. For example, the app could be installed on mobile devicesof employees of a certain workplace or on the mobile devices of studentsof a school to avoid distracting features of the mobile device such astexting, internet, or photography. The disabling signal would betransmitted by an existing or previously installed signal generator asdescribed above; however, the mechanism triggering the disabling signalwould be, for example, an physical on/off switch or a software timerthat turned the disabling signal on and off at certain times of the day,rather than motion status of the vehicle. The app would query a list, orwhitelist, of media access control (MAC) addresses to determine if areceived disabling signal is coming from a valid source as describedpreviously. Alerts such as the removal of the primary app or secondaryapp would be communicated to a monitoring party (such as the workplaceowner) device as described previously.

Having now described the invention, the construction, the operation anduse of preferred embodiments thereof, and the advantageous new anduseful results obtained thereby, the new and useful constructions, andreasonable mechanical equivalents thereof obvious to those skilled inthe art, are set forth in the appended claims.

What is claimed is:
 1. A system of limiting mobile device functionalityin a vehicle comprising: a disabling device having a motion detector, amicrocontroller in communication with the motion detector, wherein themicrocontroller receives a motion status of the vehicle from the motiondetector, a signal generator in communication with the microcontroller,wherein the signal generator transmits a disabling signal responsive toreceipt of the motion status of the vehicle indicating that the vehicleis in motion; and a mobile device for receiving the disabling signal,wherein a software application on the mobile device alters the mobiledevice's system configuration responsive to the disabling signal.
 2. Thesystem of claim 1, wherein the software residing on the mobile devicealters the mobile device's system configuration to restrict the mobiledevice's ability to send and receive text messages and email messages.3. The system of claim 2, wherein the software residing on the mobiledevice further alters the mobile device's system configuration torestrict the mobile device's ability to respond user input.
 4. Thesystem of claim 1, wherein the software residing on the mobile devicealters the mobile device's system configuration to restrict the mobiledevice's ability to place and receive phone calls.
 5. The system ofclaim 1, wherein the software residing on the mobile device furtheralters the mobile device's system configuration to restrict the mobiledevice's ability to place and receive phone calls requiring userinteraction with a touch screen or a keyboard of the mobile device. 6.The system of claim 1, wherein the disabling device further comprises acellular radio in communication with the microcontroller, wherein thecellular radio transmits an alert when a monitoring event has occurred.7. The system of claim 6, further comprising: a monitoring party'sdevice for receiving the alert from the cellular radio.
 8. A device forlimiting mobile device functionality in a vehicle comprising: a motiondetector; a microcontroller in communication with the motion detector,wherein the microcontroller receives a motion status of the vehicle fromthe motion detector; and a signal generator in communication with themicrocontroller, wherein the signal generator transmits a disablingsignal responsive to receipt of the motion status of the vehicleindicating that the vehicle is in motion.
 9. The device of claim 8,further comprising: a cellular radio in communication with themicrocontroller, wherein the cellular radio transmits an alert to amonitoring party's device when the microcontroller detects a monitoringevent has occurred.
 10. A method of limiting mobile device functionalityin a vehicle having a disabling device, comprising a motion detector,associated therewith comprising: detecting, at the motion detector, amotion status of the vehicle; transmitting a disabling signal to amobile device in communication with the disabling device as long as themotion status indicates that the vehicle is in motion, whereby thedisabling signal causes a software application on the mobile device tolimit the functionality of the mobile device.
 11. The method of claim10, further comprising: transmitting an alert to a monitoring party'sdevice in communication with the disabling device when a monitoringevent occurs.
 12. The method of claim 11, wherein the monitoring eventis when the disabling device is removed from the vehicle.
 13. The methodof claim 11, wherein the monitoring event is when the disabling deviceloses power from a power source for a predetermined period of time. 14.The method of claim 10, further comprising: polling, at the mobiledevice, for the disabling signal from the disabling device; receiving,at the mobile device, the disabling signal; and altering the mobiledevice's system configuration responsive to the disabling signal beingvalid.
 15. The method of claim 14, further comprising: receiving, at themobile device, a second disabling signal; and determining if thedisabling signal is valid; and restoring the mobile device's systemconfiguration responsive to the second disabling signal being invalid.16. A method of limiting mobile device functionality in a vehicle havinga disabling device, comprising a motion detector, associated therewithcomprising: polling, at a mobile device, for a disabling signal from thedisabling device; receiving a disabling signal; determining if thedisabling signal is valid; altering, by a software application on themobile device, the mobile device's system configuration responsive tothe disabling signal being valid; polling for the disabling signal; andrestoring the mobile device's system configuration responsive to notreceiving the disabling signal after a pre-determined amount of time.17. The method of claim 16, wherein the disabling signal comprises anidentifier.
 18. The method of claim 16, wherein altering the mobiledevice's system configuration comprises restricting the mobile device'sability to send and receive text messages and emails.
 19. The method ofclaim 18, wherein altering the mobile device's system configurationfurther comprises restricting the mobile device's ability to responduser input.
 20. The method of claim 16, wherein altering the mobiledevice's system configuration comprises restricting the mobile device'sability to place and receive phone calls.
 21. The method of claim 16,wherein altering the mobile device's system configuration comprisesrestricting the mobile device's ability to place and receive phone callsrequiring user interaction with a touch screen or a keyboard of themobile device.
 22. The method of claim 16, further comprising:transmitting an alert to a monitoring party's device when the mobiledevice's ability to limit mobile device functionality in an operatingvehicle is tampered with or disabled.